Minutes, IBIS Quality Task Group 20 September 2022 12:00-13:00 Eastern Time (09:00-10:00 Pacific Time) ROLL CALL ANSYS Curtis Clark Cadence Design Systems Yingxin Sun Intel Corporation * Michael Mirmak MathWorks [Mike LaBonte] Micron Technology * Randy Wolff SAE ITC Michael McNair Siemens EDA Weston Beal Teraspeed Labs * Bob Ross unaffiliated Mike LaBonte Zuken USA * Lance Wang Everyone in attendance marked by * NOTE: "AR" = Action Required. ------------------------------- MINUTES ------------------------------------- Bob Ross conducted the meeting. Call for IBIS related patent disclosures: - None Review of previous meeting minutes: Minutes from the 13 SEP 2022 meeting were reviewed. Michael Mirmak moved to approve the minutes. Lance Wang seconded. Without objection the minutes were approved. Call for opens: - Randy requested time to discuss IBISCHK related to checking Input models that include C_comp_pullup and C_comp_pulldown. - Bob noted we may discuss a "platform issue" message of IBISCHK AR review: - Bob Ross ask Michael Mirmak about need/solutions/priority for security fixes Michael has a bug draft providing a list of security concerns for TSCHK2 to review Bob got a response from Atul that there is not a security process for IBISCHK - Bob Ross report BUG229 resolution to Atul (add IBS prefix) Bob reported this is complete - Bob Ross work with Arpad Muranyi on new BUG report for “Waves” versus “Wave” Done. Submitted as BUG237 - Michael Mirmak supply acceptable security fixes for TSCHK2 for BUG report Done - Weston Beal work on inserting power aware rules into the Quality Specification Remains open - Weston Beal check ibischk7 V7.1.1 for relevant power aware checks Remains open - Weston Beal send draft IBIS Quality spreadsheet with added power aware checks Remains open New ARs: - None Discussion: IBISCHK711 status Michael Schaeder and Mike LaBonte provided feedback on BUG229 by email. Curtis Clark responded as well. BUG229 is complete and will be fixed in the upcoming IBISCHK7.1.1 release. BUG227 – Root Name check (action deferred until work starts on IBIS Version 7.2 Bob noted no discussion until we start on IBISCHK Version 7.2 Secure Development Lifecycle (SDL) investigation (Security fixes), (TSCHK2) Michael introduced a BUG6 draft for TSCHK2. Intel is being more rigorous about checking code brought into the company. The analysis for security is similar as code developed for internal tools. There are automated scans done on the source code. SDL questions are also asked of developers, and it assumes that teams developing codes are following SDL practices. Some code practices include: avoid buffer overruns, make sure that functions check inputs as the function executes, prevent access to any file paths, and use secure versions of print and scan functions. The question comes back to as part of our parser development process, can we be sure to use secure functions. Either Atul will need to run scanning software or one of the parser purchasers can scan the code for security issues. Lance commented there are some antivirus programs that check for buffer overflows. He showed a stackoverflow webpage with a snippet of code, and the Bitdefender Antivirus moved the code to quarantine. Bob thought Synopsys might already run code through their security process. Other vendors might be able to do the same. Lance noted IBISCHK is developed in C with an old coding style and some section of code with few comments. It would be a large project to convert to C++. Randy noted Michael plans to provide a report on critical fixes needed for IBISCHK. If a bug report can be written for IBISCHK we can scope out the complexity of security fixes for an upcoming version. We would rely on Intel to check that new code is compliant with security requirements. Bob plans to hold the BUG6 report for TSCHK2 for discussion at the next meeting. BUG237 – “Waves” versus “Wave" Illegal arguments for Rx_Impulse_Input are not always correctly reported. "Waves" was substituted for "Wave" with many variations including other parameter options. There was some position dependency in the ordering of parameters that allowed some test cases to pass when they should have failed. Bob may add a note to the bug report to check if other Reserved_Parameters with enumerated string arguments and List format use similar code and may be missing checks. Bob identified several Reserved_Parameters that should be checked. Randy commented this should be communicated to Atul by email, but not included in the BUG237 report. If other issues are found, then additional bug reports should be filed to document the code changes. The Reserved_Parameters are Modulation, PAM4_Mapping, BCI_State, BCI_Training_Mode. Bob may check one of these later. TSCHK2 V2.02 BUG5 implementation plan (on hold for any new BUG report) Bob noted BUG6 is new. New code might make sense for including BUG5 and BUG6 at some point. Quality Specification and checklist power aware discussion (continuation) No discussion Tabled topics (no discussion without motion): - None Randy moved to adjourn. Lance seconded. Without objection the meeting ended. Meeting ended: 1:02 pm ET Next meeting 27 SEP 2022